<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
    <head>
        <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
        <link rel="stylesheet" type="text/css" href="../../styles.css" />
        <title>
            CSC207H: Project, Phase II
        </title>
    </head>
    <body>
        <h1>
            CSC207H: Project, Phase II
        </h1>
        <h2>
            Due Date
        </h2>
        <p>
            Because of the extension to A2, Phase II of the project is due Monday 23 November.
        </p>
        <h2>
            Overview (regular teams)
        </h2>
        <p>
            The initial <a href="product_backlog.html">product backlog</a> has been created. In this phase, your group will do your first full sprint. There are two sprints in total.
        </p>
<p>
Remember that product backlogs are fluid, and items might appear or disappear as the project progresses.  (We won't do it to trick you; rather, changes will be used to help guide you.)
</p>
        <h2>
            Overview (service-learning teams)
        </h2>
        <p>
            Your team should probably already be well underway on development. From here on out, you need to follow the Scrum process, including the two sprints.
        </p>
        <p>
            If you don't yet have a good product backlog, make one in discussion with your client and ScrumMaster. This is due Monday 23 November at noon. <em>This is the same due date and time as for your sprint backlog, described below.</em>
        </p>
        <h2>
            Team member evaluations (both service-learning and regular teams)
        </h2>
        <p>
            By popular request, we have not given out team member evaluations for Phase I. However, they exist for Phases II and III.
        </p>
        <p>
            You will be filling out and submitting a form for each of your team members, <strong>including yourself</strong>. This form will rate team members on citizenship: did they attend meetings, did they participate, did they do what they said they were going to do, and so on. We will post a final version before the deadline. Your Phase II will receive a grade, and these evaluations will be used to make individual adjustments to that grade. <strong>These are meant to be private: each team member will hand these in separately, and you are not required to show each other your forms.</strong> In the case of serious disagreement, or if you request it, we will hold a team meeting to discuss the results, but we will never reveal individual ratings.
        </p>
        <h2>
            Sprint backlog (both service-learning and regular teams)
        </h2>
        <p>
            To start Phase II, your team needs to work out its sprint backlog: the list of items your team thinks it can accomplish in this phase, as described in <a href="lectures/L5101/w5/Scrum.pdf">Scrum</a> and on the web. Make a page on your team's wiki for the sprint backlog, and remember to include estimated difficulties. In particular, remember that the sprint backlog contains everything related to the sprint: questions your team needs to find answers for, a detailed breakdown of roughly half of the items from the product backlog, stuff you need to learn or set up, and so on. Also, this page should have two separate lists: one for tasks that still need doing, and one for tasks that are done.
        </p>
        <p>
            Your sprint backlog will be marked not only on content but also on clarity, structure (please don't make a mess), grammar, and spelling.
        </p>
        <p>
            <strong style="color:magenta">Your team should have this done by Monday 23 November at noon. The TAs will check to make sure that you have your sprint backlog prepared.</strong> (Lovely colour, isn't it? That way you can't miss it.)
        </p>
        <h2>
            User Guide (both service-learning and regular teams)
        </h2>
        <p>
            You should have a user guide prepared for the features that you have implemented.  Your user guide will be marked for effective content, style, presentation, spelling, and grammar.  Remember: you're writing for a non-technical audience, and you should have task-based organization; also, pictures and tables make life a lot easier for the reader.
        </p>
        <h2>
            "Daily" status report (both service-learning and regular teams)
        </h2>
        <p>
            In Scrum, you and your team would normally start every workday with a 10-minute meeting and give status reports. This lets you, your team, and your ScrumMaster keep track of each other and know that everyone is keeping up. (Or not!) Since you and your team are almost never all in the same room, you'll use email instead.
        </p>
        <p>
            In the week of 23 November, you need to send a total of three emails to your team and your ScrumMaster with answers to these questions:
        </p>
        <ul>
            <li>What did you accomplish since the last report?
            </li>
            <li>What do you plan to do in the next couple of days?
            </li>
            <li>What obstacles are in your way?
            </li>
        </ul>
        <p>
            The three emails <strong>must</strong> go out during these time periods:
        </p>
        <ul>
            <li>First email: after Sunday at 3pm and before Monday at noon.
            </li>
            <li>Second email: after Tuesday at 3pm and before Wednesday at noon.
            </li>
            <li>Second email: after Thursday at 3pm and before Friday at noon.
            </li>
        </ul>
        <p>
            The obstacles are technical obstacles. Don't, for example, list other classwork or other time pressures. Instead, list problems specific to the project, like "I can't get <a href="RecStore.java">RecordStores</a> to work." and "I'm having trouble getting NetBeans on CDF to save my project settings.". The ScrumMasters will try to help with these obstacles, and if they can't, they'll let Paul know.
        </p>
        <p>
            Emails must be clear, effectively structured, and contain proper spelling and grammar.  Bullet points are fine.
        </p>
        <h2>
            The end of the sprint (both service-learning and regular teams)
        </h2>
        <p>
            At the end of the sprint, your team should have a working version of a mobile application that does a substantial part of the product backlog. You should, of course, have Javadoc comments for all your code.
        </p>
    </body>
</html>
